Contents
1 Introduction
2 How to improve server performance
A) Operating system side consideration
B) Domino Application server side consideration
3 Maintaining Domino Environment Best Practice
4 Debugs for collecting Troubleshooting Data.
5 Notes.ini Variables for debugs and DCT
6 Troubleshooting Tips.
7 Conclusion
8 Resources
9 About the Authors.
10 Trademarks.
1.Introduction
The overall business objective of this document is to identify area of potential improvement and provide recommendations in effort to increase
the performance of the existing Domino servers. With this regards we will focus on the following areas:
• The Domino server assessment.
• The operating system assessment.
Performance is stands for tuning the existing resources to obtain the optical performance for domino. As domino is an application to the OS
it has also dependency on CPU, Memory & Disk I/O.
2.How to improve server performance
Server performance can be an issue from OS side or Domino application side. So please always follow the below recommended steps for the same.
A)Operating system side consideration
1> Always keeps minimum 30% free for better disk I/O and the server performance for the IBM Domino data drive partition.
2> Make sure the disk Average queue length of the data drive should always less than 2. Also If the value of Avg. Disk Queue Length exceeds twice the number of spindles,
then you are likely developing a bottleneck. With a volume set, a queue that is never shorter than the number of active physical disks indicates that you are developing a bottleneck.
https://technet.microsoft.com/en-us/library/cc938625.aspx
3> Always check if the number of Task and DB Task are under the limits of the OS threshold.
4> Perform fine tuning to improve AIX server in areas of paging, memory management and CPU utilization and load balancing.
5> Perform periodical server restart to refresh server cache and memory.
6> Always keep physical hardware CPU of this server to 4 CPUs or at least to 2. Server will gain significant performance improvement when running mail routing, Agents, http processes and other Domino tasks.
7> Avoid performance problems by disabling TCP global settings that are available in Microsoft Windows Server 2008 and later.
1. If we have large number of users in your organization it is always good to implement cluster feature. Server A is the only mail server serving over 2900 users,
consider having a server B as cluster member server to provide fail over and load balancing.
2. There are some redundant server tasks running on the server, we recommend perform diligent maintenance of Domino server, remove unwanted mail files,
monitor regular server statistics and review unnecessary server task such as fixup and updall.
3. Remove unnecessary Notes.ini parameters such as debug parameters, any unwanted entries such as the “comment out” entry and including the Concall/Sched
task entry on domino servers. These parameters beside consume server resources also might cause confusion if there are too many comments out parameters.
4. Create private network on cluster server to ease the server resource and network traffic congestion.
5. Increase Domino directory cache lookup to improve server performance.
6. Remove or modify un-necessary connection document to free up server resources.
7. Investigate potential Domino problem such as Semaphore timout before becoming serious.
8. Remove or modify Domino web logging if necessary to improve web server performance.
9. Review Domino server feature such type ahead if necessary remove it but ensure will not compromise business objective.
10. Review Notes client feature such as LZ1 compression attachment and enable it if necessary.
11. Modify Domino server mail file directory structure to enhance server performance and ease day to day server administration.
12. Review any setting and configuration of Internet Information Server (IIS) and SiteMinder to ensure that none of the current setting compromise Domino performance.
13. Perform regular Domino server monitoring and analyses to identify any potential problem.
14. To save network bandwith and improve general server performance you can disable the type-ahead mail addressing feature. If you disable type-ahead addressing on a mail server, users can still use type-ahead addressing to find addresses in their Personal Address Book or mobile Directory Catalog.Process to disable type-ahead on a server, open the server's Configuration Settings document in the Domino Directory. On the Basics tab, choose Disabled in the Type-ahead field. Then save and close the document.
15.Always setup proper number of mail.boxes on the server . Please find the below how to calculate the number of mail.boxes required .
Mail.Mail.box.Accessconflicts/Mail.Mailbox.Accesses) x 100 > 2 with this calucalation we can check if it required to increase or decrese the number of mail box on the server.
16. We should also look at the Server Availability Index.
Link::http://www.ibm.com/support/knowledgecenter/SSKTMJ_9.0.1/admin/admn_theserveravailabilityindex_t.dita?lang=en
17. NLCache_Size=n, where n equals the name lookup cache size in bytes.
Domino Version | OS | recommended NLCACHE_SIZE value | Remarks |
Domino 8.5.1
Domino 8.5.2 | Windows 2003_x32 | 96MB | use 64 MB, on performance problems you can increase to 96 MB |
Windows 2003_x64 | 96MB | on 64 bit platform you can use 96 MB or previous recommendations of 128 MB |
RedHat Enterprise Linux 5.4 | 96MB | on 64 bit platform you can use 96 MB or previous recommendations of 128 MB |
Domino 8.5.3 | Windows 2003_x32 | 96MB | use 64 MB, on performance problems you can increase to 96 MB |
Windows 2003_x64 | 96MB | on 64 bit platform you can use 96 MB or previous recommendations of 128 MB |
Windows 2008_x64 | 96MB | on 64 bit platform you can use 96 MB or previous recommendations of 128 MB |
RedHat Enterprise Linux 5.4 | 96MB | on 64 bit platform you can use 96 MB or previous recommendations of 128 MB |
RedHat Enterprise Linux 6 | 96MB | on 64 bit platform you can use 96 MB or previous recommendations of 128 MB |
For optimal performance, the size of this cache needs to exceed the maximum that will occur under normal situations. We recommend to increase the size to double 32MB (33554432) for a start and monitor the cache lookup statistic again. The
Impact would be the that this cache would consume more memory which is 32MB that otherwise could be used for other Domino task, but any additional memory will not be used.
For 32-bit server configurations with 2GB total memory, NLCACHE_SIZE should be set to 64MB (default for 8.5.X) and increased only if performance problems are experienced with
users complaining of inability to perform initial server connections (usually database opens getting hourglasses).
You can increase according the the following list incase of a performance issue:
20. Always recommend to be on latest server release as most of the bugs are fixed.
3.Maintaining Domino Environment Best Practice
This appendix describes best practices for maintaining Domino environment.
Recommended maintenance schedule
A major part of every Domino administrator’s job is maintaining the Domino servers. You need to ensure that:
· The server is backed up regularly.
· Users can access the server quickly and consistently.
· Mail is routed properly.
· Administration Process requests are carried out.
· Databases are replicating correctly.
· Server hardware is functioning.
· Databases are active and maintained.
Daily monitoring checklist
You should perform the following tasks on a daily basis:
1. Check server accessibility and availability:
· Check that all required services on the Domino servers are running.
· Ping the servers’ IP address.
· Use a server monitoring tool, such as Tivoli, Percussion, or DYS, to check for server availability outages.
2. Review the STATISTICS database:
This database should be leveraged to see day-to-day activity and should be visited right after server accessibility:
· Look at the Alarms view:
This view provides a snapshot of alarms generated by Notes, based on the threshold settings defined in the Statistics Monitoring. Information logged here is the most critical to examine first. Define a procedure for follow-up on these areas such as trouble tickets or some other follow-up mechanism.
· Look at the Events view:
This view provides a snapshot of threshold events based on the Statistics Monitoring defined above. Define a procedure for follow-up on these areas such as using trouble tickets or some other follow-up mechanism.
3. Review the Notes Log database:
· Review all views:
Use the Log Analysis tool to search these views effectively. Define search strings
specific to problems such as process starts and stops, failed processes or error
conditions, corruption problems, network problems, agent manager problems, security problems, SMTP problems.
· Replication events views:
You should focus on the Replicator initiating server, for example the replication hubs. Use the Notes search tool to find problem areas such as failed replications due to ACL issues, server availability and network problems.
· Mail Routing Events view:
Generally this view only needs to be looked at if you have known mail delivery
problems such as Domino-to-Domino mail routing or Domino-to-Internet mail routing.
4. Check MAIL.BOX(es) on all servers:
Look at Pending or Dead mail, although the Statistics & Events should have captured this first. Perform a Refresh on the Database to make sure that mail is moving.
5. Server tasks:
First ensure that all general tasks that all servers need are running, then look at:
· Mail server(s) specifically
· SMTP mail server(s) specifically
· Application server(s) specifically
· Review tasks either through the Domino 6 Administrator.
· Use a Web browser to make sure that access to the HTTP process for mail is working.
6. Did daily backups complete successfully?
Incorporate a backup matrix that shows what backups went successfully.
7. Check SMTP mail routing — test that SMTP mail is functioning properly:
· Check Internet to Domino/Domino to Internet mail routing.
Use an account originating from each Notes Named Network (validate $MIMEtrack in Document properties to track server hops).
· Check that Internet mail can be held in mail queues.
Check the MAIL.BOX(es) on the Domino SMTP servers for dead or pending mail. Domino monitoring can be leveraged, for example, configure the Domino events monitor to notify your administrators if there are more than 500 e-mails pending in a MAILx.BOX on your Domino SMTP server.
· Check Mail queues on Internet mail relay servers.
· Check Mail queues on Virus Scanning SMTP servers.
8. Check daily server downs:
Recycle Domino servers to maintain performance. This is not as necessary on the iSeries platform as on other Domino platforms.
Weekly server tasks
You should perform the following tasks on a weekly basis:
1. Monitor disk space utilization and consumption patterns:
Log weekly the amount of used versus free disk space for charting. This will show disk space consumption trend activity — when to add more disk space or reduce file sizes. Make sure threshold values have been set using Statistics Monitoring.
2. Weekly Domino server backups:
· Verify that all backups completed successfully during the week. Note any backup problems - have a process for follow-up on backup issues.
· Check that backups are stored offsite.
· Check if replication between recovery servers and mail servers has completed successfully.
3. Database maintenance routines:
· Check to make sure all FIXUP, UPDALL, and COMPACT routines have run successfully. Look for databases that need maintenance, for example, check the Database/Sizes view in the Notes Log to see %Used and database size. Use COMPACT and UPDALL on databases with more than 10% white space, identified as databases with less than 90% Used.
· Verify that the Design task ran successfully. Verify that there are no missing templates.
4. Check server statistics for performance and availability:
Look at server health using whatever tool(s) available. Check statistics for disk consumption and mail usage (Domino and SMTP) to identify trends and devise proactive plans for maximizing performance and availability.
5. Cluster analysis:
Run the Cluster Analysis in the Domino 6 Administrator weekly to find out problems. The most common issue is to make sure that all replicas exist on the correct servers. Run Cluster Analysis from the Server -> Analysis tab in the Domino 6 Administrator. Click Tools -> Analysis -> Cluster on the right hand side of the window to display the Cluster Analysis prompt window. Select the appropriate options for your analysis, then review the output.
6. Messaging usage:
· Document the number of inbound and outbound Internet messages delivered and the size of messages, including message transfer times. It is important to understand when messages leave your site to the Internet domain to verify you meet the SLA established with your user community.
· Document the number of Notes messages delivered and the size of messages. You need this information for planning and proactive actions required for your environment.
Monthly server tasks
You should perform the following tasks on a monthly basis:
1. Scheduled server downtime:
· Perform any activities that require a server to be down.
· Perform database maintenance on the NAMES.NSF, BUSYTIME.NSF, CATALOG.NSF, NOTES.LOG, CLDBDIR.NSF databases.
· Perform MAIL.BOX maintenance. Rename the mail.box(es) to mail.old, then let the Domino server create new mail.box(es) when it restarts. Copy any undelivered messages to the new mail.box(es).
2. Review recurring problems:
Develop action plans to address any recurring problems in your environment or make plans to avoid potential problems.
3. Test backups and the validity of data restoration:
Check for good data restoration. Verify if it can be used effectively and reliably.
4. Review monthly server statistics for performance and availability:
Look at server health using whatever tools are available. Check statistics for disk consumption and Notes and SMTP mail usage to identify trends and devise proactive plans for maximizing performance and availability.
5. Run a Cluster Analysis:
Run a monthly Cluster Analysis in the Domino 6 Administrator to uncover any problems not previously identified in the weekly analysis. Identify trends and devise proactive plans for maximizing performance and availability, if needed.
4.Debugs for collecting Troubleshooting Data.
Here is the steps we take if you have an Server Performance issue in the future:
1. SET CONFIG CONSOLE_LOG_ENABLED=1 (Instructs the Domino Server to write console data to console.log in the IBM_TECHNICAL_SUPPORT directory. This information is very valuable when working with IBM Lotus Support for server issues)
2. SET CONFIG DEBUG_THREADID=1 (causes the Domino Server to log information in the format: [ProcessID:Virtual Thread IDNative Thread ID] This information is very valuable when working with IBM Lotus Support for server performance issues)
3. SET CONFIG DEBUG_CAPTURE_TIMEOUT= 1(Domino Server to log semaphore time stamps to semdebug.txt. This information is very valuable when working with IBM Lotus Support for server performance issues)
4. SET CONFIG DEBUG_SHOW_TIMEOUT= 1( Domino Server to log semaphore information to semdebug.txt. This information is very valuable when working with IBM Lotus Support for server perfomance issues)
If You have performance issues due to Memory Then we suggest to enable below debugs in notes.ini of the server
5. DEBUG_SHOWLEAKS=1
6. DEBUG_TRAPLEAKS=0311
7. DEBUG_TRAPLEAKS_SHOWSTACK=1
8. DEBUG_TRAPLEAKS_NEW=1
9. DEBUG_DUMP_FULL_HANDLE_TABLE=1
http://www.lotus-expert.com/en/notes-ini-reference/760-debug_showleaks.html
Noted here few publish document which you can refer while collecting basic information
Working on server performance issues.
Collecting data for Lotus Domino Server hang/bad performance
http://www-01.ibm.com/support/docview.wss?uid=swg21447230
Collecting data for HTTP hang or performance issues on a Lotus Domino server
http://www-01.ibm.com/support/docview.wss?uid=swg27010969
Title: How to run a manual NSD for Notes/Domino on Windows
http://www.ibm.com/support/docview.wss?uid=swg21204263
Title: How to run NSD manually on a Domino server for UNIX platforms
http://www.ibm.com/support/docview.wss?uid=swg21214298
Debug / Logging Parameters that have Performance Impact:
Crash and Performance: · Full Text indexing: Debug_FTV_Search=1
Debug_FTV_Index=1
Debug_FT_Stream=1 · TCPDebug_Tcp_All=1
Relating to which database is being opened, and by which user: Technote 1090972 DEBUG_NOTEOPEN=5
Core:
Task Debug Technote
Compact | debug_dbcompact-1 | 1096160 |
Update/Indexer | log_update=1,2 | 7002624 |
| debug_nif_update | 1101655 |
Replication | log_replication=1,2,3,4,5 | 7002968 |
Archiving | debug_archiving=0 | 1313174 |
Archiving | debug_archiving=1 |
Archiving | debug_archiving=10 |
Archiving | debug_archiving=11 |
AdminP | debug_adminp=1 | 1099388 |
Name Lookup | debug_namelookup=1 | 1093215 |
Agent Manager Task | debug_amgr=1 | 1115204 |
Agent Manager Task | log_AgentManager=1 | 1115204 |
Replication Debug Parameters
Replication Information | debug_repl=1 | 1158590 |
| debug_repl_all=1 | 1158590 |
| debug_repl_dump | No TechNote |
| debug_repl_full_search | No TechNote |
Smart Upgrade messages | debug_Smart_Upgrade=1 | 1139893
|
Policy Debug Parameters | debug_policy | 1206188 |
| debug_dynconfig | 1206188 |
| debug_ClientRecord | 1206188 |
| debug_policy_create | 1206188 |
| debug_policy_synopsis | 1206188 |
Client:
Client_clock=1 (Client_Clock=1 Enables the RPC's (from the client to a server) to be outputed to a file or the screen )
LOG_CONNECTIONS=1 (When connection logging is enabled on a server, the server console displays the name of the IBM ® Lotus ® Notes ® network port for TCP/IP, the IP address of the requesting system, and the IP address of the destination server for each connection.
Mail Routing:
Nothing noted as high impact on performance for any parameters unless the parameters are left enabled longer than needed. (size and disk space consumption that will grow over time if left enabled. )
|
|
5A.Notes.ini Variables for debugs.
·
ALWAYS create a safe, backup copy of the notes.ini (for Domino Server especially) before introducing changes.
·This information is provided in an effort to provide our customers with the relevant information required for performing this task. It is beyond the scope of work of IBM Support to edit your environment's notes.ini file in the process of identifying obsolete parameters and maintaining your specific Notes/Domino implementation. Other software venders' products require custom configurations to the notes.ini, and IBM Support can not be made responsible for configuring another vendor's product. For updates on notes.ini parameters added by third party products, contact the respective vendor directly.
Maintaining NOTES.INI settings related to troubleshooting:
Many Notes/Domino issues require additional debug parameters to be added to the notes.ini that are not present by default. When working with IBM Support, engineers request that certain debug parameters be added to the notes.ini to provide detailed information that is necessary in troubleshooting your issue. Support engineers will generally supply the information and required steps to enable and disable these debug parameters. When the requested data has been collected and received, the Support engineer will suggest that the added debug parameters be disabled or removed from the notes.ini.
Debug parameters affect product performance, so you want to maintain a list of all parameters adding during the troubleshooting phase so that these may be easily removed when the issue is resolved.
Best practice: Regularly scan the notes.ini--especially after troubleshooting an issue-- for debug parameters that are no longer needed, and disable or remove them completely . Some debug parameters can cause very verbose information to be logged to the console.log causing the console log file to grow in size quickly which could take up an unnecessary amount of disk space.
http://www-01.ibm.com/support/docview.wss?uid=swg21328649
5B.The Domino Configuration Tuner (DCT)
What is DCT?
The Domino Configuration Tuner (DCT) helps administrators effectively and efficiently review
their Domino configurations to ensure that best practices are employed, lowering total cost of
ownership.
DCT is intended to provide customers with easy-to-use self-service configuration analysis so that their installations are more robust and experience better performance. A single Domino server includes thousands of configuration options. DCT provides best practice analysis as well as worst practice disclosure. It is our expectation that DCT will help reduce total cost of ownership by assisting in the identification of existing configuration problems.
DCT looks at settings in Server documents, NOTES.INI, and database advanced properties. Configuration settings are flagged when their values are know to cause problems based on prior customer experience. Out-of-range and unexpected values are reported so that undefined behavior can be prevented. Suggested adjustments help administrators achieve known server performance improvements.
How does it work?
Run and installed via the Domino Configuration Tuner database
Updated by online template updates and rule updates
DCT rules and results are held in a local database and will require a
restart of the client for changes to take effect
Scans
Server documents
notes.ini settings
advanced database properties
Intended to scan servers in a single domain
Creates reports on each scanned server based on the rules you select
Each report contains Issues recommendations for adjustments
links to supporting documentation.
https://www-10.lotus.com/ldd/dominowiki.nsf/dx/domino-configuration-tuner
http://www.dannotes.dk/dannotes/arrangem.nsf/0/4da3ff91b522a080c12575040046b057/$FILE/Dannotes_DCT.pdf
6.Troubleshooting Tips.
The following tips will help Administrators to optimize their Notes/Domino environment. It is important for Administrators to understand that any configuration change should be closely monitored for its effects. Make single changes at a time to ensure adverse effects are easy to spot and changes can be backed-out.
1. We have seen view rebuilds dtf files are getting generated in data directory on server which is causing performance down on this server so enable below notes.ini on server
view_rebuild_dir=
X:path to desired directory
.DTF files are temporary files that are created by Domino in a temporary directory specified by the system's environment variable. The format is "S0-S9" or "IDB", followed by a unique five-digit number. These files are normally purged from the system automatically and if there is no Temp or Tmp directory specified, the files are placed in the working directory. Files placed in the working directory are not purged.
Every time the Update task runs, it creates view files in the Data directory that start with the letter "S" and have a .dtf extension. These files can also be created in the notes.ini file View_Rebuild_Dir directory. When the Update task ends, all the files should be purged automatically. If the files are not removed, it is likely that the Update task never ended, perhaps because the server crashed while Update was running possibly by running out of disk space.
Refer this publish document
Lotus Software Knowledge Base Document
Title: Can the default directory where the "update" task rebuilds views be changed?
Doc #: 1090462
URL:
http://www.ibm.com/support/docview.wss?uid=swg21090462
2.Temp files we need to keep in out of data directory this parameter Notes_tempdir=
path to desired directory out of data directory
Refer this publish document
Title: Can you specify where Notes stores temporary files?
Doc #: 1175587
URL:
http://www.ibm.com/support/docview.wss?uid=swg21175587
View Index Updates
It is possible to tune the Domino update task to take advantage of the additional CPU resource of multi-core hardware. There are a several NOTES.INI parameters that you may use:
Update Task (View Index Updates)
If the system’s resources allow it, additional Update tasks may be started on the server, by adding the parameter, Updaters=[number], to the NOTES.INI. As a rule of thumb, do not exceed a maximum of one Update task per CPU. For example, to enable two Update tasks, apply this parameter:
· Updaters=2
Full Text Index Updates
A separate thread can be created solely for full text updates. This separate thread will only be responsible for updating full text indexes, so view updates will continue to occur even if a large full text index is being rebuilt. Consider applying this NOTES.INI parameter if many full text indexes are present on a Domino server and sufficient CPU resource remain:
· UPDATE_FULLTEXT_THREAD=1
Maintaining view indexes
The NOTES.INI parameter DEFAULT_INDEX_LIFETIME_DAYS=[number of days] allows administrators to set a default lifetime for database view indexes if none was selected by the database designer in the Design View Attributes dialog box.
The default value for this parameter is 45. Setting this to a lower value can have two benefits:
· Save Disk Space
· Reduce amount of work Update task must perform
Creating view indexes is disk intensive and requires CPU and memory resource, so it is important for Administrators and designers to strike a balance. It is not recommended to set this value to lower than 14 (two weeks).
Disable Transaction Logging For Certain Databases
Turning transaction logging may impact your enabled DAOS features relative to mail. In most cases, disabling Transaction Logging is not recommended because you lose the benefits of fast server restart. Disabling transaction logging on a database will cause Fixup to run on that database, creating the potential for slow restart. Furthermore, you will not be able to perform incremental backups using the transaction logs for that database.
For some databases, however, it might not be necessary to enable transaction logging. This is because it generates additional transaction log traffic on the disk and causes the transaction log drive to fill up quicker. Examples of databases that are suitable for disabling of transaction logs are:
· Mail boxes (mail.box) - Do not disable Transactional Logging on Mail.boxes if you are running DAOS.
· Server Log (log.nsf)
· Monitoring Results (statrep.nsf)
· Statistics Mail-in (statmail.nsf)
· Web Administration (webadmin.nsf)
· Schedule (clubusy.nsf or busytime.nsf)
· Cluster Database Directory (cldbdir.nsf)
·
HTTP Server Threads
In order for you server to function properly it must be able to handle all of the requests it receives. Domino provides a number of statistics to help you determine the health of the Domino web server. For example, to determine the peak number of threads used by the web server review the statistic
Domino.Threads.Active.Peak. By default, the number of active threads is 40. However; if you are using all available threads and have available memory for additional threads you can increase this value in the server document,
Internet Protocols... →
HTTP tab, Number of active threads parameter as shown in figure 1.
The Domino web server queues requests as they come in so they can be processed by the HTTP server threads. In some cases changing the queue method used can improve performance.
HTTP Requests
When tuning your server, it helps to understand what requests are being processed on your servers. You can do this by
logging Domino web server requests. Thus, you can access this information "after the fact" by reviewing the
access logs and/or the web log database
domlog.nsf. You enable logging for your server in Internet Protocols tab of the server document as shown in figure 2.
In order to see which requests are being processed in "real-time" you can use the Domino command
tell http show thread state. This will present you a list of all active threads and the URL currently being processed if the thread is not idle. Below are two example entries and you can see that the first thread is idle and the second thread is opening the Inbox for User One (uone.nsf).
11/18/2010 12:09:28 Http Worker Thread ID [1c7]: [Thread State is Idle]
11/18/2010 11:18:12 Http Worker Thread ID [2425]: Working session [9a732]: Session State [Processing Request] : GET /mail/uone.nsf/iNotes/Proxy/?OpenDocument&Form=s_ReadViewEntries&PresetFields=DBQuotaInfo;1,FolderName;($Inbox),hc;%24Sender1%7C%2498,UnreadOnly;1&TZType=UTC&Start=1&Count=23&resortdescending=1 HTTP/1.1
If your server is struggling to process all requests due to database contention, view index rebuilds or database corruption, you will see all requests showing the same database, view or document. This is a fast and simple way for you as an administrator to identify potential database issues. In other cases, you may see that all of the pending requests are agents. By default, only 1 agent can process at a time. However; if the agents running on your server are thread-safe, then you may modify the configuration of the server to allow multiple web agents to run concurrently. To make the change, open the server document and access the Internet protocols... → Domino Web Engine tab. Change Run web agents and web services concurrently to Enabled as shown in figure 3.
JVM Heap
The default JVM Heap can be modified using the NOTES.INI parameter HTTPJVMMaxHeapSize.
If you are using XPages, you will want to increase the size of the heap at 8.5.2 and higher. If you are not using XPages and running 8.5.1, you will want to decrease the default size. More information can be found in
http://www-01.ibm.com/support/docview.wss?uid=swg21377202
Database Performance
When working with the Domino web server and applications, the same techniques to improve database performance from a Lotus Notes client can be used on the web. For a list of the most common reasons for slow database performance refer to
http://www-01.ibm.com/support/docview.wss?uid=swg21174563
7.Conclusion:
Customers and Software engineer who is reviewing this document should have a good feel for solving and troubleshooting Domino server performance issues on your own,
which will help you to be self-sufficient and, in turn, reduce the turn-around times for problem resolution.
8.Resources and References
IBM DeveloperWorks technical articles:
Optimizing Server Performance. Port Encryption and Buffer Pool Settings.
www.ibm.com/developerworks/lotus/library/ls-Port_encryption/
Best Practices for Large Lotus Notes Mail Files.
https://www.ibm.com/developerworks/lotus/library/notes-mail-files/
Optimizing Server Performance: Semaphores (Part 1)
http://www.ibm.com/developerworks/lotus/library/ls-Semaphores_Part1/Optimizing Server Performance: Semaphores (Part 1)
http://www.ibm.com/developerworks/lotus/library/ls-Semaphores_Part2/How to reduce the size of Domino Web Server Log (domlog.nsf).
http://www-01.ibm.com/support/docview.wss?uid=swg21161104How does the notes.ini file parameter 'server_session_timeout' affect server performance
http://www.ibm.com/support/docview.wss?uid=swg21293213
Domino Server performance troubleshooting best practices
https://www10.lotus.com/ldd/dominowiki.nsf/dx/Domino_Server_performance_troubleshooting
9.About the authors
Seema Janjirkar is a Senior Software Engineer with more than 14 years of
experience working in the Domino environment. She is a Certified Lotus Professional
(CLP) and information Technology Infrastructure Library (ITIL) Certified.
Deepankar Panda is a Senior Software Engineer with more than 13 years of
experience working in the Domino environment He is a Certified Lotus Professional (CLP)
& ITIL V3 Foundation certified.
10.Trademarks
•Developer Works, Domino, IBM, Lotus, and Notes are trademarks or registered
trademarks of IBM Corporation in the United States, other countries, or both.
•Microsoft and Windows are registered trademarks of Microsoft Corporation in the
United States, other countries, or both.
•Other company, product, and service names may be trademarks or service marks of others.